Convert .dtd variform overrides to .xml variform overrides

If you are upgrading from any version of N4 below 2.2, immediately after the upgrade, you must change the header lines in all of your overridden variforms to refer to the .xsd schema. If you do not do this, you will see the following errors when testing:

Error log examples:

[REQUIRES IMMEDIATE MANUAL ATTENTION: db-backed variform record 'test' needs to be converted to use new schema 'Variforms.xsd'. Please correct problem once the application starts.

[REQUIRES IMMEDIATE MANUAL ATTENTION: db-backed variform record 'test'. Validation exception: xxx ]. Please correct problem once the application starts.

If you are upgrading previously-scoped forms, N4 preserves the scope on import. You do not need to re-specify scope for your database-backed variforms. Pre-2.2 variforms with no scope default to Global scope. Therefore, if you are upgrading from a version of N4 that did not allow scoped overrides, you can review your override forms to identify whether it makes sense to restrict scope at this time.

To convert .dtd variform overrides to .xml variform overrides:

  1. In the Database Backed Variforms view (Administration Settings Database Backed Variforms), double-click an overridden variform.

  1. In the Variform File Definition form, replace the .dtd header information with the .xml string, as follows:

  1. Above the Contents Edit Area, click Edit Contents. The Contents Edit Area becomes editable.

  1. If applicable, replace the following lines:

<!DOCTYPE variforms PUBLIC "" "Variforms.dtd">

<variforms>

with

<?xml version="1.0" encoding="UTF-8"?>

<variforms xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="schemas/Variforms.xsd">

  1. Click Save.

N4 validates your changes and alerts you to any validation issues. If no issues occur, the Edit Variform File Definition form closes.

  1. If errors occur while saving the form, correct the errors. N4 does not save the form if there are validation errors.

  1. Repeat step 2 for all records in the Database-Backed Variforms list.

  2. After changing all records in the list, select Actions Reload All Variforms. The Variforms Reset form appears.

  3. In the Variforms Reset form, select the Only update local node option to test the form locally before propagating the changes to all nodes. This is strongly recommended.

Only select the Propagate changes to all nodes option after testing the changes locally.

  1. Click OK. The Variforms Reset form closes, and the new forms are propagated to all nodes.